Hi,

>> 1) To fix the foundation and once and for all 
>>   the GPFs on all platforms / compiler 
>>   supported by hbide / QT.
>> 
> 
> Here, perhaps, we need Przemek's help.
> I did whatever I could thought. I have requested
> Przemek for some clarifications, the answer to 
> which may lead to resolving this issue.
> 
>> 2) To fix .ini file handling to be standard.
>> 3) Related: Merge dangling secondary .ini and similar 
>>   config files into the central .ini.
>> 
> 
> Why we are concerned about these points, BTW ?

Because this is what can make hbide different from 
the other (loosely engineered) ide's that one can 
find on the internet.

Because it shows that you/we pay attention to details, 
and care about the product.

Because this is the spirit we follow when designing 
other parts of Harbour.

Because current static update method doesn't play 
when in multiuser scenarios. (f.e. hbide is shared 
on a network drive, or used in a terminal server 
environment)

Just to name four. BTW, you asked for improvements 
requests, and this one is IMO an important one.

> It is an application and developer knows best his 
> abilities/shortcomings. This is how I could implement 
> all the coordinates I needed. Cassle is built and changing 
> the foundation is difficult if not impossible. 

Never impossible. Now it's a straight no brainer 
as not many ppl are using hbide yet.

> All other config files can  makeup into the central 
> file. because of their different formats. .tag, .skl, .env
> has some specific differences. May be someone can help
> to merge them.

It's not an 'all or nothing' thing. Just don't use 
additional files unless absolutely necessary, that's 
all.

Did you try HB_INI*() functions?

BTW, we're not even obliged to use a relatively 
complicated .ini format. A simple flat format 
is much easier to handle. F.e. this one also 
stays compatible with .ini standard:

F.e.:
---
[hbide]
global.MainWindowGeometry=-4,-4,1291,814,
global.ProjectTreeVisible=1
global.FunctionListVisible=0
global.RecentTabIndex=-1
global.CurrentProject=
global.GotoDialogGeometry=
global.FindDialogGeometry=
global.CurrentTheme=City Lights
global.CurrentCodec=
global.PathMk2=
global.PathEnv=
global.CurrentEnvironment=
global.CurrentFind=
global.CurrentFolderFind=
global.CurrentReplace=
global.CurrentView= Stats
CurrentHarbour=
PROJECTS=F:\work\harbour\harbour\contrib\hbide\config.hbp,...
FILES=
RECENTFILES=f:/work/harbour/harbour/contrib/hbide/idetags.prg;f:/work/harbour/harbour/contrib/hbide/ideeditor.prg;f:/work/harbour/harbour/contrib/hbide/idedocks.prg
RECENTPROJECTS=f:/work/harbour/harbour/contrib/hbide/hbide.hbp
---

You can easily add the QT settings to that format.

>> 4) Related: To solve storing settings on *nix 
>>   platforms. On these platforms you don't 
>>   store settings in .ini file in current dir.
>> 
> 
> I do not know the behavior of nixes in this regard.
> If ".ini" extension is the concern, we can change
> them to somethng else. Some nix user has to 
> jump in.

It's not the extension, it's the placement.

Probably '${HOME}/.hbide' should be the dir 
to store .ini-like stuff on *nix. On Windows, 
this could be '%APPDATA%\.hbide' dir, on OS/2 
I don't know.

As for "resources" stuff, I don't know, probably 
best would be to incorporate all of them right 
into the executable in some ways, otherwise hbide 
will need an installer to place these to the 
expected on platform location. Or some *nix 
users will give better ideas.

>> 5) To use hbmk2 for format conversion.
>> 
> 
> This is not a big issue. I will do in next commit.

Thanks.

>> 6) To make the decision: .ui or .uic and stick to 
>>   only one.
>> 
> 
> .uic. It is the only format in use currently.

I can see .ui files in SVN. If they are not used, 
maybe they can be deleted to avoid confusion.

>> 7) Future: To honor formatting and original comments 
>>   when saving .hbp files.
>> 
> 
> Yep, absolutely needed.

OK.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to