> the original issue that I have noticed in some other place in our code is :
> namespace core // our namespace for exemple
> {
> /// lift boost smart pointers into core namespace
> using boost::shared_ptr;
> }
>
> then our pointer are declared
> core::shared_ptr<object>
Right that doesn't work yet. I think our code model master was working on
that.
>
> 2) Plugins
> we are a fairly large team of developers and if usage of QtCreator takes
> off (like I hope) it might be worth for us to write couple of customs
> plugins for QtCreator to integrate it better to our workflow , is there
> plugins tutorial or one of the plugins that is easy to understand that I
> should look at to see what is possible ?
Well, writing your own plugins is not easy. There's a pretty decent
introduction to some of the Creator internals written by an external.
See http://www.vcreatelogic.com/resources/downloads/ on the tab Other
downloads.
Also some classes are documented either in their header/source file.
And the "Hello World" plugin (enable it in src/plugins.pro) shows some very
simple stuff.
But for the most part, there's not much stuff to get you started writing your
own plugin. Also be warned that Creator's internal APIs change often and quite
dramatically at times.
Also while our code is pretty readable, it can be hard to figure out how the
different plugins interact. And we are probably missing the interface for what
you want to do, so you might need to add new APIs to the existing plugins.
In summary: Writing your own plugins is currently not easy at all.
Now that you have been warned, several people have succesfully written their
own plugins. If you explain a little bit what you are trying to achieve and
have some code, we can hopefully give you better information on where to look.
And explain why it's implemented in that way.
> 3) Project Template
> we have couple of project type we can build and it would be great if we
> could make template that would show up in "create New Project UI" ? is
> that possible , changing the code and re-building qtCreator wouldn't be
> a problem ?
Yes that would be possible, probably the best place to start is looking at
GenericProjectWizard, because that does the work in a straight forward way.
As usual in Creator, GenericProjectWizard is actually a factory for the wizard
that pops up if you select import generic project. There's only one instance
of GenericProjectWizard, and that one instance gets added to the object pool.
Every time the user selects "import new makefile project" the
createWizardDialog() is called, which should return a QWizard derived classes
implementing your own Wizard. The extension pages, are pages like adding stuff
to version control.
generateFiles() should create the actual files and return a list of them. (So
that they can be added to e.g. to version control.)
postGenerateFiles() is called at the end and for most project wizards, that
simply opens the project.
> 4) Syntax Highlight for Namespace ?
> I am getting greedy I guess but it would be very usefull for us to
> hightlight the Class coming from a certain Namespace into certain colors
> . I can see that it is not possible at the moment but I would be
> interested to see if its possible without too much work , could someone
> point me in the general direction ( files , class I need to look at ?)
Hmm, the current highlighter uses the Tokenizer from the cpp tools, but not
all of the code model. The code for that is in CppHighlighter::highlightBlock
That code does not try to to find the correct namespace for each symbol.
And I'm no expert on that code, and thus don't know how that could be
implemented. Though iirc, I think there was some plans to extend the code
hightlighter to use more information from the code model. Also the
hightlighting of locals unused variables is done in a different place. Hmm.
daniel
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator
