Thanks for answering Craig!
Well... What I'm looking for is a way to split a huge class in several small
files (I can't create new classes). The problems (for me. it's not a bug or
anything, just what I was hoping would be there, kkkk) with the #include
directive as it is currently implemented are
1) It does not point errors and outline to the source files, but to the
huge class file (and there's no tool to take me there either). So if I want
to edit something, I have to find the code in the small file by myself.
2) I can't use some jdt functionalities in the small files. For example, if
I forget a ";" or if I make some other small mistake, I don't know right
away; only after the code is inserted in the big class file (I guess this is
a bit more complicated :P).
Well... This is it. Just so you know, as it is the #include directive is
already helping a lot. I was wondering if there's any plan to improve it
with the features I listed above. Or if someone here knows of a tool I can
use to achieve similar results.
Thanks,
Cesar
On Dec 15, 2007 11:43 PM, Craig Setera <[EMAIL PROTECTED]> wrote:
> Cesar,
>
> I'm a bit confused about what you are looking for. Could you give a bit
> more information about what you would like to see versus what is
> currently there? To some extent, all of EclipseME is a work in
> progress, but even so things do generally work as expected.
>
> Craig
>
> Cesar Castro wrote:
> > Hi All,
> >
> > I just subscribed to the mailing list and did a search on the subject,
> > but could not find what I was looking for. If there's a discussion on
> > the matter, please forgive me (and give me a link please, kkkk).
> >
> > I'm working on a big project with a few other developers and we could
> > really use a way to divide a class in several files, since in mobile
> > applications adding classes cause undesirable problems of space
> > and speed. Since we all love and use EclipseME, the #include
> > preprocessor directive seems like a good way of accomplishing that.
> > But I've noticed it's still a work in progress. Simply copying the
> > text, which is what happens now, does not work very well, since in big
> > files, it's not obvious from which file (and position in that file) a
> > particular piece of code came from.
> >
> > Could you guys tell me what are the plans for this feature in future
> > EclipseME releases? Or maybe suggest a tool to get the same results?
> >
> > Thanks in advance.
> >
> >
> > Cheers,
> >
> > Cesar Castro
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > SF.Net email is sponsored by:
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Eclipseme-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> >
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
>
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Eclipseme-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Eclipseme-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
