templar4522:
It actually saves files on Ctrl + S, it just doesn't update the title. I've already fixed it :)
Could you tell me the critical error? They are kind of a big deal :P Do you use x64?
If you're getting those importing errors, it might be because of you using x64. You can delete those files though.
I need your system specs in order to know why these stuff happen. Do you have the .net framework 4.0? x64? What OS?
Kalekin:
It's not built on top of VS :P (Atleast it's not an extension, it's just inspired by it) Extensions are already implemented, I'm writing documentation for how to do it. Basically you create a .dll, which has (xx) number of user controls, exporting data through the MEF framework:
If you're having a background extension, Hidden should be true, else the UserControl would be added as a dock window to the program. (Or a tab if Dock is DockStyle.Fill)
In order to interact with the native user interface in Moonlite, I've created a "language" known as Ximl. Here's an example:
<?xml version="1.0" encoding="utf-8" ?>
<Ximl TargetType="TestExtensionWindow" Namespace="TestExtension">
<Ribbon>
<RibbonPage Caption="Addins">
<RibbonPageGroup Caption="Test Addin" ShowDialogLauncher="false">
<Button Caption="Large Message!" Name="btnLargeMessage" Image="TestExtension.Icons.message.png" Size="Large" OnClick="OnLargeMessageButtonClick">
<ToolTip Caption="Large Message!" Content="Trust me, this one is huge!" />
</Button>
</RibbonPageGroup>
</RibbonPage>
</Ribbon>
<QuickAccessToolbar>
<Button Caption="A Button" Name="testButton" Image="TestExtension.Icons.home.png" OnClick="OnWindowTestButtonClick">
<ToolTip Caption="This is a tooltip caption" Content="Hello from the tooltip! Seems you hovered over the Home button, huh?" Image="TestExtension.Icons.MoonliteBig.png">
<Footer Content="This is the footer." Image="TestExtension.Icons.MoonliteSmall.png" />
</ToolTip>
</Button>
</QuickAccessToolbar>
<StatusBar>
<Text Caption="Message from the Test Extension Window extension!" Name="testExtensionWindowLabel" OnDoubleClick="OnWindowLabelDoubleClick">
<ToolTip Caption="Text with tooltip" Content="Static text messages can have tooltips, too." />
</Text>
</StatusBar>
</Ximl>
The documentation will include API documentation, because Moonlite has a lot of stuff extension authors can use.
doos101:
Try running as administrator. In future versions the installer and program will ask for administrator permissions, but in this release you have to run as administrator.
Also guys, I am doing a lot of bug fixes, but I need you to report any issue you're experiencing.
I have also been brainstorming a little. Here are my ideas so far:
Auto recovery – saves projects into a backup directory every (x) minutes and if Moonlite crashes, the user will have an option to recover the “unsaved” project.
Code insight – a dialog on top of the editor window that has “insight” into the current file. Holds stats such as number of lines, number of methods, number of properties, etc. When the user hovers over for example the text saying “Properties: (x)”, a textbox should popup giving the type, name and signatures of the given objects.
Change Ribbon interface to Toolbar interface in order to save space and have a more IDE like and intuitive layout.
Add Build messages to the statusbar in order to indicate that the program is building the project rather than it has frozen.
Add an “Object Browser” for having a tree view of for example the stdlib’s classes/enrichments/structs. A class/enrichment/struct’s members can also be viewed.
Floating run button – having a Test Map button right next to the text editor instead of the top of the screen in order to make the distance the user has to move the cursor smaller.
Template toolbox – a dock window that contains a list of code templates. A code template is represented as an item that can be dragged into your code. When the item is dropped, the code of the item will be inserted at the place the item was dropped. Templates could be added via files (like the File Templates in the current Templates directory in the installation directory), so that the user can add custom made templates. The templates would use a special template markup language, e.g: “if (<cursor index=”0” />) {
<cursor index=”1” />
}”
This would make the user’s cursor be first set to the “if” statement’s condition statement, and when he pressed a given “tabbing” key (maybe Ctrl + Shift + Right arrow key), the cursor would go to the next cursor statement.
NOTE: the template toolbox idea has been changed to be keyboard supportive. Instead of drag-drop, it would require you to for example write "if" and then it would generate the template.
Well... Like I was saying, come release Moonlite won't be real necessary, and sparsile in it's current form will also be unnecessary. The difference is, sparsile is ridiculously flexible, so it can be changed to do whatever they need.
MilkyWayEdit, on the other hand, it a own Editor entirely. I really like Moonlite, I just don't believe it'll be worth the development time since it's features will be in GE.
Though back to your original point, yes, things will really need to wait until GE goes live.
Moonlite is also very flexible. It has the same extension engine as Visual Studio 2010.
I'm not gonna let Moonlite fall to the ground. It might not be the best there is, but I have used incredible amounts of time on this (1,5 year), so I will keep improving it until it's the best.
Official Moonlite website
Moonlite (or Moonlite Map Studio) is an IDE (Integrated Development Environment) for StarCraft 2 and WarCraft 3. Currently it only supports scripting and file import management, but it will also support object scripting, debugging and maybe even terraining. It also is 100% extensible, as it uses the same extension engine as Microsoft Visual Studio 2010.
It is currently in a rather early stage, meaning that crashes and issues can happen. A bug reporter tool is included, but please, only use it if the issue you have found really is a bug. (Meaning that the most people I have had using it so far has tried to use a feature, done it wrong and told me there's a bug)
Since it is an open beta, please also always keep a backup of the map you're editing. Although Moonlite creates a backup, the backup is used for dynamic syntax checking, so just have a backup to be sure.
I haven't finished the documentation yet, so it's not included. If you're used to using the Visual Studio IDE, you'll find using Moonlite easy. To code with it, you simply create a new project, and then add files to that project. Moonlite uses files that it then compiles into the map. If you want to script an already existing map, you have to create a new project, build it, and replace the map in the Bin directory of the project's directory by the map you want to edit. Preferably you want to replace all your GUI triggers by Moonlite code, but it should be compatible.
Moonlite is tightly integrated with the Andromeda language, meaning that it 100% supports OOP programming. Because of this, Moonlite supports dynamic error checking and intelligent and context sensitive code completion. (The code completion isn't implemented yet though)
Note that I want all the feedback, suggestions and error reports I can get. Although this is beta software it should be in a pretty stable state.
The current Galaxy features are:
100% Andromeda support;
Dynamic error checking;
Xml object creating through Xml files;
Code completion (yet to come)
The current Jass features are:
100% vJass support;
Dynamic error checking;
Code completion (Finished)
There are probably more independent language features, but I most likely forgot.
Global features:
Project manager;
Function list;
Live code preview;
Rich user interface;
Object Browser;
and more
The Andromeda code completion will feature enrichment support, inheritance support, class support, etc. For example, say we have a static class named "Test" with fields "op" and "offset". In our code, we can write "Test.", and when the dot is typed, a list of the members in the Test class pops up. Very small example, but it should do justice to get you thinking.
Requires the .NET Framework 4.0!Download link: http://www.vestras.net/moonlite/download/
The source code is currently not available. It will be available as soon as the application gets out of beta stage.
If you are experiencing any installation problems, but tell me in this thread ASAP.
For developers, the installer is custom created using WPF and a zip extracter. All files are packaged into zip packages/embedded resources.
DISCLAIMER: I take no responsibility for any damage this software does to you or your computer, your maps or any project that you have created. Any issues with your computer, your maps or any project that you have created caused by Moonlite is your own problem.
PS: It seems like the editor can't insert newlines after links. Kinda annoying.
0
templar4522:
It actually saves files on Ctrl + S, it just doesn't update the title. I've already fixed it :)
Could you tell me the critical error? They are kind of a big deal :P Do you use x64?
If you're getting those importing errors, it might be because of you using x64. You can delete those files though.
I need your system specs in order to know why these stuff happen. Do you have the .net framework 4.0? x64? What OS?
Kalekin:
It's not built on top of VS :P (Atleast it's not an extension, it's just inspired by it) Extensions are already implemented, I'm writing documentation for how to do it. Basically you create a .dll, which has (xx) number of user controls, exporting data through the MEF framework:
[Export("Moonlite.Composition.WindowExtensionContract", typeof(UserControl))]
[WindowMetadata(Dock = DockStyle.Bottom, DockId = 0, Hidden = false, Name = "Test Extension Window")]
If you're having a background extension, Hidden should be true, else the UserControl would be added as a dock window to the program. (Or a tab if Dock is DockStyle.Fill)
In order to interact with the native user interface in Moonlite, I've created a "language" known as Ximl. Here's an example:
<?xml version="1.0" encoding="utf-8" ?>
<Ximl TargetType="TestExtensionWindow" Namespace="TestExtension">
<Ribbon>
<RibbonPage Caption="Addins">
<RibbonPageGroup Caption="Test Addin" ShowDialogLauncher="false">
<Button Caption="Large Message!" Name="btnLargeMessage" Image="TestExtension.Icons.message.png" Size="Large" OnClick="OnLargeMessageButtonClick">
<ToolTip Caption="Large Message!" Content="Trust me, this one is huge!" />
</Button>
</RibbonPageGroup>
</RibbonPage>
</Ribbon>
<QuickAccessToolbar>
<Button Caption="A Button" Name="testButton" Image="TestExtension.Icons.home.png" OnClick="OnWindowTestButtonClick">
<ToolTip Caption="This is a tooltip caption" Content="Hello from the tooltip! Seems you hovered over the Home button, huh?" Image="TestExtension.Icons.MoonliteBig.png">
<Footer Content="This is the footer." Image="TestExtension.Icons.MoonliteSmall.png" />
</ToolTip>
</Button>
</QuickAccessToolbar>
<StatusBar>
<Text Caption="Message from the Test Extension Window extension!" Name="testExtensionWindowLabel" OnDoubleClick="OnWindowLabelDoubleClick">
<ToolTip Caption="Text with tooltip" Content="Static text messages can have tooltips, too." />
</Text>
</StatusBar>
</Ximl>
The documentation will include API documentation, because Moonlite has a lot of stuff extension authors can use.
doos101:
Try running as administrator. In future versions the installer and program will ask for administrator permissions, but in this release you have to run as administrator.
Also guys, I am doing a lot of bug fixes, but I need you to report any issue you're experiencing.
I have also been brainstorming a little. Here are my ideas so far:
<cursor index=”1” />
}”
This would make the user’s cursor be first set to the “if” statement’s condition statement, and when he pressed a given “tabbing” key (maybe Ctrl + Shift + Right arrow key), the cursor would go to the next cursor statement.
Suggestions/ideas are welcome.
NOTE: the template toolbox idea has been changed to be keyboard supportive. Instead of drag-drop, it would require you to for example write "if" and then it would generate the template.
0
Moonlite is also very flexible. It has the same extension engine as Visual Studio 2010. I'm not gonna let Moonlite fall to the ground. It might not be the best there is, but I have used incredible amounts of time on this (1,5 year), so I will keep improving it until it's the best.
0
Official Moonlite website Moonlite (or Moonlite Map Studio) is an IDE (Integrated Development Environment) for StarCraft 2 and WarCraft 3. Currently it only supports scripting and file import management, but it will also support object scripting, debugging and maybe even terraining. It also is 100% extensible, as it uses the same extension engine as Microsoft Visual Studio 2010.
It is currently in a rather early stage, meaning that crashes and issues can happen. A bug reporter tool is included, but please, only use it if the issue you have found really is a bug. (Meaning that the most people I have had using it so far has tried to use a feature, done it wrong and told me there's a bug) Since it is an open beta, please also always keep a backup of the map you're editing. Although Moonlite creates a backup, the backup is used for dynamic syntax checking, so just have a backup to be sure.
I haven't finished the documentation yet, so it's not included. If you're used to using the Visual Studio IDE, you'll find using Moonlite easy. To code with it, you simply create a new project, and then add files to that project. Moonlite uses files that it then compiles into the map. If you want to script an already existing map, you have to create a new project, build it, and replace the map in the Bin directory of the project's directory by the map you want to edit. Preferably you want to replace all your GUI triggers by Moonlite code, but it should be compatible.
Moonlite is tightly integrated with the Andromeda language, meaning that it 100% supports OOP programming. Because of this, Moonlite supports dynamic error checking and intelligent and context sensitive code completion. (The code completion isn't implemented yet though) Note that I want all the feedback, suggestions and error reports I can get. Although this is beta software it should be in a pretty stable state.
The current Galaxy features are:
The current Jass features are:
There are probably more independent language features, but I most likely forgot.
Global features:
The Andromeda code completion will feature enrichment support, inheritance support, class support, etc. For example, say we have a static class named "Test" with fields "op" and "offset". In our code, we can write "Test.", and when the dot is typed, a list of the members in the Test class pops up. Very small example, but it should do justice to get you thinking.
Requires the .NET Framework 4.0! Download link: http://www.vestras.net/moonlite/download/ The source code is currently not available. It will be available as soon as the application gets out of beta stage. If you are experiencing any installation problems, but tell me in this thread ASAP. For developers, the installer is custom created using WPF and a zip extracter. All files are packaged into zip packages/embedded resources.
DISCLAIMER: I take no responsibility for any damage this software does to you or your computer, your maps or any project that you have created. Any issues with your computer, your maps or any project that you have created caused by Moonlite is your own problem.
PS: It seems like the editor can't insert newlines after links. Kinda annoying.