Fwd: Some explanations/suggestion on plasmate

Diego Casella ([Po]lentino) polentino911 at gmail.com
Thu May 28 20:51:02 CEST 2009


Well, I forwarded the message I sent today to morpeuz about some ideas on
plasmate.
Take a look, then tell me what you think about =)

---------- Forwarded message ----------
From: Artur Souza(MoRpHeUz) <artur.souza at openbossa.org>
Date: 2009/5/28
Subject: Re: Some explanations/suggestion on plasmate
To: "Diego Casella ([Po]lentino)" <polentino911 at gmail.com>


Hi Diego!

On Thursday 28 May 2009, 07:34 you wrote:
> a class declaration ). So, I was wondering if could I continue on riccardo
> code, adding all the basical function needed ( such as init,clone, pull,
> diff, apply, status, checkout and commit ).

Maybe it's a good idea to send an email do plasma-devel so others can also
give
their opinions on this one. I didn't take a look on Vng so I can't argue
here
very much. I'm just afraid that in the end we have to reimplement a lot of
things that are already in Vng....

>    1. run the git -add comand  every time a new file is created, and then
>    run it every x minutes, defined by user from a form named "autosave",
> then run git -commit when the developer click on "save file" button. (
very
> ugly, I know )
>    2. run git -add when the user press the "save file" button, and call
git
>    -commit when "save project" is pressed, displaying a box for inserting
>    informations on the commit. ( this makes more sense, but from the point
> of view of simplicity, there are too "save something" buttons )

Hmmm...another idea would be to have an "Add File To Project" like Kile and
other editors have. This way the "new files situation" is solved. Regarding
files
that are already being tracked, we should just add them all and then commit
when the auto save interval times out. If the user wants to put a message in
his commit, we can have a "Save With Description" option or something like
that...

But again, let's see what ideas people on plasma-devel have ;)

> A solution could be implementing the previewer as a tabbed widget, and put
> it together with the other  editor tabs, so the coder first edit all the
> files needed, then change to the preview tab to see the result =)
> Or, we can add an auto show/hide feature to the dock widget, so it pops-up
> only when needed.

The preview tab may work and I agree that maybe keeping the previewer open
all
the time may waste screen space...

Cheers! :)

---------------------------------------------------------------
Artur Duque de Souza
OpenBossa Research Labs
INdT - Instituto Nokia de Tecnologia
---------------------------------------------------------------
Blog: http://labs.morpheuz.eng.br/blog/
GPG: 0xDBEEAAC3 @ wwwkeys.pgp.net
---------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/plasma-devel/attachments/20090528/a7694ae2/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090528/a7694ae2/attachment-0001.sig 


More information about the Plasma-devel mailing list