Olivier Sessink | 1 Aug 2007 10:17
Picon
Gravatar

Re: making the development branch the new stable branch

Daniel Leidert wrote:
> Am Dienstag, den 31.07.2007, 19:40 +0200 schrieb Olivier Sessink:
> 
>> since bluefish development is very slow right now, we should try to make 
>> the development version stable, so more people can use all the new 
>> options in the development branch.
>>
>> so what should be the roadmap? can we call the current version stable, 
>> or do we need to fix things first?
> 
> I think, we still miss some things in the External menu atm. IMO the
> filters and commands sub-menus are still empty.

they are user-configurable, but indeed, we should provide a good default 
set of commands.

> I would further like to see plugin loading/unloading on demand

that's a major change. I would like to postpone that.

 > to allow
> loading of plugins depending on the opened file-type (I already started
> a discussion about this in the past). Otherwise our plugin style won't
> be that power- and useful.

true

> I further suggest to find a way to handle things on Cygwin. I sent the
> mail, what we need to do, some time ago. I still have a copy of it
> locally.
(Continue reading)

Daniel Leidert | 1 Aug 2007 11:14
Picon

Re: making the development branch the new stable branch

Am Dienstag, den 31.07.2007, 16:30 -0600 schrieb Steve:
> On Wed, 01 Aug 2007 00:05:24 +0200
> Daniel Leidert <daniel.leidert.spam@...> wrote:
> 
> > > Also, syntax coloring for *.css files is pretty much non-existent.
> > > (BTW, bluefish 1.1.3 incorrectly identifies *.css as c source files,
> > > but manually changing the document type and hitting f5 doesn't
> > > change the syntax coloring.)
> > 
> > Hm. Are you sure, that isn't a problem in (your)
> > shared-mime-info/gnome-vfs? Because the MIME type in css.bflang is
> > correct, I currently cannot think of a problem inside bluefish. Don't
> > we simply use gnome-vfs to determine the filetype?
> > 
> > Can you provide the special CSS file? Can you tell, what gnomevfs-info
> > thinks about this file? Maybe try it with the -s option to to force
> > slow detection (uses some more checks).
> > 
> That's it. If the *.css file begins with a /*...*/
> comment, gnomevfs-info reports it as text/x-csrc, without the comment
> it's text/css. With the comment removed, Bluefish figures it out just
> fine.

Can you tell me, which version of gnome-vfs and shared-mime-info are you
using? I cannot reproduce the issue (gnome-vfs 2.18.1 and
shared-mime-info 0.22). Looking into the upstream ChangeLog of
shared-mime-info I find:

> 2007-02-05  Bastien Nocera  <...>
> 
(Continue reading)

Daniel Leidert | 1 Aug 2007 11:24
Picon

[Fwd: Cygwin: Plugins loading functions from the executable fail to load (sample solution patch attached)]

Here the mail about making pplugins work on Cygwin. Defining EXPORT in
the mail has directly been fixed (so not shipping my mistake from the
original mail)

-------- Weitergeleitete Nachricht --------
> Von: Daniel Leidert <daniel.leidert.spam@...>
> Antwort an: bluefish-dev@...
> An: ml_bluefish-devel <bluefish-dev@...>
> Betreff: Cygwin: Plugins loading functions from the executable fail to
> load (sample solution patch attached)
> Datum: Mon, 27 Nov 2006 07:10:41 +0100
> 
> Hi,
> 
> As mentioned several times before, all plugins except the About plugin
> fail to load on Cygwin/Windows (with an "Permission denied" error).
> Therefor I tried to find the reason and a solution and found
> http://www.mingw.org/docs.shtml#compilingandbuilding [1] and several
> other documents. Reading from this I wrote a small testcase, that loads
> a function tstfunc(), defined in bluefish.{c,h}, into the About plugin,
> so I can follow, if it also fails. It did. Then I tried the
> __declspec(dllexport)/__declspec(dllimport) stuff from the above
> document (see the attached patch and the about.def) and now it loads the
> plugin. So we need to implement this for all plugins that load functions
> >from the executable or these plugins will never be loaded under
> Cygwin/Windows. Ideas for a standard way to do this? Maybe
> 
> #ifdef WIN32_BUILD_EXE
> #define EXPORT __declspec(dllexport)
> #ifdef WIN32_BUILD_DLL
(Continue reading)

Daniel Leidert | 1 Aug 2007 11:25
Picon

Re: making the development branch the new stable branch

Am Mittwoch, den 01.08.2007, 10:17 +0200 schrieb Olivier Sessink:
> Daniel Leidert wrote:

[..]
> > I further suggest to find a way to handle things on Cygwin. I sent the
> > mail, what we need to do, some time ago. I still have a copy of it
> > locally.
> 
> I cannot find the mail, can you send it again?

Forwarded to the list.

Regards, Daniel

Steve | 1 Aug 2007 21:15

Re: making the development branch the new stable branch [Spam Score: 2.3]


> Can you tell me, which version of gnome-vfs and shared-mime-info are
> you using? I cannot reproduce the issue (gnome-vfs 2.18.1 and
> shared-mime-info 0.22). Looking into the upstream ChangeLog of
> shared-mime-info I find:
> 
gnome-vfs 2.18.1
shared-mime-info .19

I just upgraded shared-mime-info to .21r1 (Gentoo's most recent), and
the problem went away.

Regards,

Steve

--

-- 
Steve Jacobs
Trinidad graphics
www.trinidadcolorado.net
Trinidad, CO US
Elve | 23 Aug 2007 22:52

Dutch translations

I have finished dutch translations for the CVS version (1.1.3), but i don't know
where to send it. The mailaddress on the site don't work

Daniel Leidert | 23 Aug 2007 23:49
Picon

Re: Dutch translations

Am Donnerstag, den 23.08.2007, 20:52 +0000 schrieb Elve:
> I have finished dutch translations for the CVS version (1.1.3), but i don't know
> where to send it. The mailaddress on the site don't work

Send it to this list. Here are enough people with commit permissions :)

Regards, Daniel

elve | 24 Aug 2007 11:05

Re: Dutch translations

Daniel Leidert schreef:
> Am Donnerstag, den 23.08.2007, 20:52 +0000 schrieb Elve:
>   
>> I have finished dutch translations for the CVS version (1.1.3), but i don't know
>> where to send it. The mailaddress on the site don't work
>>     
>
> Send it to this list. Here are enough people with commit permissions :)
>
> Regards, Daniel
>
>   
Ok, here they are:

regards Eric
Attachment (bluefish-unstable.po): text/x-gettext-translation, 52 KiB
Attachment (bluefish-unstable_plugin_about.po): text/x-gettext-translation, 3326 bytes
Attachment (bluefish-unstable_plugin_entities.po): text/x-gettext-translation, 2544 bytes
Attachment (bluefish-unstable_plugin_htmlbar.po): text/x-gettext-translation, 56 KiB
Attachment (bluefish-unstable_plugin_infbrowser.po): text/x-gettext-translation, 3465 bytes
Attachment (bluefish-unstable_plugin_snippets.po): text/x-gettext-translation, 6538 bytes
R Kimber | 25 Aug 2007 18:08

save all problem

I'm using the 31 July snapshot.

I had a problem with "save all"

I opened a large number of files (I'm not certain how many but
certainly > 1500) I did an edit on all files, and then did a 'save all',
and ended up with quite a large number of 'File save failed' windows
superimposed on each other (maybe 300-400).

One problem here is that there is no way of proceeding, other than
clicking OK on a very large number of windows, or killing Bluefish.

Having clicked on all the windows, I then did "save all" again, and the
previously unsaved files were then saved as normal.

Since I own all the files and the owner can read and write them all,
there seems no reason why the save all failed for some files.  Is there
a limit within the program on the number of files that can be saved by
this method?

If there is a necessary limitation, it would be nice if one could abort
all the error windows in one move, or perhaps only allow that number of
files to be opened.

- Richard.
--

-- 
Richard Kimber
http://www.psr.keele.ac.uk/
Daniel Leidert | 25 Aug 2007 23:26
Picon

Re: Dutch translations

Am Freitag, den 24.08.2007, 11:05 +0200 schrieb elve:
> Daniel Leidert schreef:
> > Am Donnerstag, den 23.08.2007, 20:52 +0000 schrieb Elve:
> >   
> >> I have finished dutch translations for the CVS version (1.1.3), but i don't know
> >> where to send it. The mailaddress on the site don't work
> >>     
> >
> > Send it to this list. Here are enough people with commit permissions :)
> >
> > Regards, Daniel
> >
> >   
> Ok, here they are:

Thanks and committed (with a few changes to fix missing copyrights in a
few files and fix the project ID and such po-header stuff). I took a
quick look into them: You translations don't contain any mnemonics? Is
this intended? I see, that also the outdated translation doesn't contain
any mnemonic. Maybe you should add them.

Regards, Daniel


Gmane