Date   

Re: Drag in EmptyDataView

Frederik Soete
 

Hi Govert,

Maybe, just maybe, it could work if the virtual is defined with the property 'Part of DataView' set to 'No'? This is just a wild guess though.

Op ma 2 dec. 2019 09:52 schreef Govert Schipper <govertschipper@...>:

Hi group,

(Using xpa 3.2d:)
One of our programs is an online task with a table control and some buttons. 
We also use an image control to drag and drop some contents. 
When the task has an EmptyDataView (which is allowed) dragging the image control onto the table seems to be disabled.
We tried different approaches such as using a virtual for the image control but nothing seems to work.
Any thoughts?

Govert Schipper


Drag in EmptyDataView

Govert Schipper
 

Hi group,

(Using xpa 3.2d:)
One of our programs is an online task with a table control and some buttons. 
We also use an image control to drag and drop some contents. 
When the task has an EmptyDataView (which is allowed) dragging the image control onto the table seems to be disabled.
We tried different approaches such as using a virtual for the image control but nothing seems to work.
Any thoughts?

Govert Schipper


Re: Gigaspaces deployment issue #xpa

Joseph Knickerbocker
 

Thank you very much Andreas, you pointed me in the right direction. In the end, it seems like you can't deploy Gigaspaces exactly like the broker, with just the dll and config file on the external-iis pointing to the broker residing on the internal-iis. I ended up using IIS + URL Rewrite + ARR as a reverse proxy. This should hold up until the traffic hits a certain load, then I will have to go for a more sofisticated reverse proxy I fear.


Re: Can Any one Help Me that How to Use TFS With XPA 3.2D ?

Andreas Sedlmeier
 

On Sat, Nov 30, 2019 at 07:23 PM, Florian Groothuis wrote:
- Create an account for TFS (Azure nowadays)
- Create a project on your TFS webspace and make sure it's version control type is set to Team Foundation Version Control. Named it preferably the same as your application
- Open your application
- Choose >File>Version control>Add to VC-server and walk through the screens

I think this is about it.
Thats how it is with other development tools. For Legacy stuff like Magic you need the MSSCCI provider and that only works with Team Explorer 2013 + Visual Studio SP5.
Those are only not available anymore. Unless you have a MSDN subscription. 

Andreas


Re: Can Any one Help Me that How to Use TFS With XPA 3.2D ?

Florian Groothuis
 

I'm using TFS for a few years now and without any real problems. Setting it up could be a bit tricky at first but when you have it al set up it will be running smoothly.

- Create an account for TFS (Azure nowadays)
- Create a project on your TFS webspace and make sure it's version control type is set to Team Foundation Version Control. Named it preferably the same as your application
- Open your application
- Choose >File>Version control>Add to VC-server and walk through the screens

I think this is about it.

You can also work the other way around, putting all XML's on your TFS-projects and then choose Open from server form within XPA, but that is slightly more tricky.



DON'T export your application, create a new one on TFS and then import it. This will take for ever for every program to check in (manually)


Re: Can Any one Help Me that How to Use TFS With XPA 3.2D ?

Andreas Sedlmeier
 

Hi Madhav,

There's issues with TFS. It's also pretty complicated to get it work releliable and if it keeps running when MS upgardes the version like recently to TFS 2019 is another question.
If you really want: http://kb.magicsoftware.com/articles/bl_Reference/Making-Magic-xpa-work-with-Team-Foundation-Server-xpa-3x

If you are fine with VSS I would keep using it, besides there's some other options for MSSCCI compliant version control.

Xpa 4.6 has native Git support as far as I know. I would go for that and just dont touch TFS

Best regards,

Andreas


Re: Repository structure in Magic Xpa / Unipaas #tools #mgpivot

Andreas Sedlmeier
 

On Fri, Nov 29, 2019 at 07:04 PM, Roberto Gauer wrote:
We had contact with a MS support engineer that shared with us this table where team explorer 2013 is on "general support" for online azure services.
 
Team Explorer 2013 does however not have very much to do with Magic Xpa. You just need it to get the MSSCCI provider work (next to Visual Studio 2013 SP5).
So for Magic there's no TFS support at all. Just scroll down in that document , There's a section "MSSCCI support" and thats what relevant for Magic and other legacy applications.
Magic Xpa 4.6 has Git support as far as I know. That would work with Azure Devops too then

Best regards,

Andreas


Re: Table in a subform

for no reason
 

choices.

If subform is always open then on parent prefix first cycle enter subtask and pass a variable
that triggers an activity.

just one example that worked for me.


Can Any one Help Me that How to Use TFS With XPA 3.2D ?

Madhav saran
 

Hello Every One,
I want to use TFS with Magic XPA 3.2D but i don't know how to use this .
I'm still using VSS with my project but i want to upgrade. 
But i don't know how to do this .
can any one help me how to do this..?


iOS app crashing with NSCFString error #-1

mykahon@...
 

Hi fellow Magicians,

We have a mobile application that works both on iOS and Android. All programs work on both platforms except for one in iOS which throws an [__NSCFString characterAtIndex]: Range or index out of bounds. The same program is working fine on Android.

Has anyone experienced this? Any suggestion on how to troubleshoot this is greatly appreciated. Thanks all!


Re: Repository structure in Magic Xpa / Unipaas #tools #mgpivot

Roberto Gauer
 

We had contact with a MS support engineer that shared with us this table where team explorer 2013 is on "general support" for online azure services.


On Fri, Nov 29, 2019 at 11:18 AM Roberto Gauer via Groups.Io <gawarez=gmail.com@groups.io> wrote:
Hi all :)

Anyone here using xpa with obrigatory provider and team explorer 2013 for tfs, and having connections issues with a online azure devops organization? 



On Mon, Mar 4, 2019 at 4:48 AM Andreas Sedlmeier <sedlmeier@...> wrote:
Hi Becky,

The only constraint for TFS Express is: 5 developers or less. As soon as your development requires a six'th person to access TFS, you need to migrate to the regular TFS version.

Install TFS Express on any server you have access too and be sure to test the installation with a MGCSTK (Magic) license. You cannot test it with Single User edition.

You'll need (on every machine where you want TFS access from Magic) an installation of MSSCCI Provider for TFS 32-Bit).

Now for me its years ago that I did such an installation so I cannot tell much about the versions you should choose. Following seems to be the latest MSSCCI Provider for TFS:
https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer20132015M

That supports Microsoft Visual Studio Team Foundation Server 2005, 2008, 2010, 2012, or 2013. Thats not the latest version of TFS I suppose so if it works with that ... I dont know.

You also need to check re the TFS source repository requirements for Magic. It needs to be server workspaces and you need to set that flag which dis-allows multiple checkouts, ...

Good luck :)

Andreas

P.S.: You would be better off with a cloud installation of TFS (Azure DevOps)


Re: Repository structure in Magic Xpa / Unipaas #tools #mgpivot

Roberto Gauer
 

Hi all :)

Anyone here using xpa with obrigatory provider and team explorer 2013 for tfs, and having connections issues with a online azure devops organization? 



On Mon, Mar 4, 2019 at 4:48 AM Andreas Sedlmeier <sedlmeier@...> wrote:
Hi Becky,

The only constraint for TFS Express is: 5 developers or less. As soon as your development requires a six'th person to access TFS, you need to migrate to the regular TFS version.

Install TFS Express on any server you have access too and be sure to test the installation with a MGCSTK (Magic) license. You cannot test it with Single User edition.

You'll need (on every machine where you want TFS access from Magic) an installation of MSSCCI Provider for TFS 32-Bit).

Now for me its years ago that I did such an installation so I cannot tell much about the versions you should choose. Following seems to be the latest MSSCCI Provider for TFS:
https://marketplace.visualstudio.com/items?itemName=TFSPowerToolsTeam.MicrosoftVisualStudioTeamFoundationServer20132015M

That supports Microsoft Visual Studio Team Foundation Server 2005, 2008, 2010, 2012, or 2013. Thats not the latest version of TFS I suppose so if it works with that ... I dont know.

You also need to check re the TFS source repository requirements for Magic. It needs to be server workspaces and you need to set that flag which dis-allows multiple checkouts, ...

Good luck :)

Andreas

P.S.: You would be better off with a cloud installation of TFS (Azure DevOps)


Re: Table in a subform

przemm@...
 

Hi John,

Not an answer you are looking for, but If you could change the subform table's row higlight style to Frame, it would at least be less pronounced , and perhaps less confusing to users ...

BR
Przemek


Re: MagicXPA45 Webclient install failure

Masanobu Tanda
 
Edited

That’s really helpful!
 
Tanda from Japan

2019年11月29日(金) 17:43 Oded Lavee <oded.lavee@...>:

hi guys
 
Any issue you might have, please contact me directly and i will do a remote session with you to check it out
 
Oded
 

 

 


Re: MagicXPA45 Webclient install failure

Oded Lavee
 

hi guys

Any issue you might have, please contact me directly and i will do a remote session with you to check it out

Oded


Re: MagicXPA45 Webclient install failure

Andreas Sedlmeier
 

On Thu, Nov 28, 2019 at 08:17 PM, Florian Groothuis wrote:
A subdirectory or file D:\Projects\XPA46\ngSPA already exists.
Most of your warnings you could safely ignore. That however not.
Now I dont know that cli, if it however reports that the directory already exists it probably does not install anything.
And ... no package no party.

What was the command you typed to get that output you pasted ?
Try a new install from within an empty directory.

Andreas


Re: MagicXPA45 Webclient install failure

Rob Westland
 

I build an app following the lessons on magicweb.io.

After logging in I route the user to a Welcome screen. This works good in 4.5, but in 4.6 it doesn't work anymore. So I thing there is a problem with routing in 4.6. I reported it to Magic, but still waiting for an answer.


Rob

On 28-11-2019 20:05, Florian Groothuis wrote:
I have a feeling that there is something buggy with either the latest Angular version or XPA46. 
Today I did the SPA-tutorial. All went well until routing came up. As soon as XPA's routing comes in play Chrome shows blank pages. I also tried my own simple app, same thing. Opening page is just fine, a button routing to a new program fails. 

The app.routes.ts shows:

export const routes: Routes = [
 
    {
        path: 'Login',
        component: RouterContainerMagicComponent,
        outlet: 'MainOutlet',
 
    },

The Chrome-debugger shows:

core.js:6014 ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'Login'
Error: Cannot match any routes. URL Segment: 'Login'



And I have to make a demo in a few weeks...


Re: MagicXPA45 Webclient install failure

Florian Groothuis
 

Also some errors on compiling the initial project:

Generation warnings/errors:
A subdirectory or file D:\Projects\XPA46\ngSPA already exists.
npm WARN saveError ENOENT: no such file or directory, open 'D:\Projects\XPA46\ngSPA\package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open 'D:\Projects\XPA46\ngSPA\package.json'
npm WARN ngSPA No description
npm WARN ngSPA No repository field.
npm WARN ngSPA No README data
npm WARN ngSPA No license field.
 
npm WARN deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
npm WARN rollback Rolling back readable-stream@2.3.6 failed (this is probably harmless): EPERM: operation not permitted, lstat 'D:\Projects\XPA46\ngSPA\SPA\node_modules\@angular\compiler-cli\node_modules\fsevents\node_modules'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
 
npm WARN The package @magic-xpa/cli is included as both a dev and production dependency.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
 
npm WARN deprecated core-js@2.6.10: core-js@<3.0 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated text-encoding@0.7.0: no longer maintained
npm WARN ng-dynamic-component@3.1.2 requires a peer of @angular/common@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-dynamic-component@3.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @magic-xpa/angular@4.6.0 requires a peer of ng-dynamic-component@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @magic-xpa/angular@4.6.0 requires a peer of rxjs@^6.5.2 but none is installed. You must install peer dependencies yourself.
npm WARN @angular/http@7.2.15 requires a peer of @angular/core@7.2.15 but none is installed. You must install peer dependencies yourself.
npm WARN @angular/http@7.2.15 requires a peer of @angular/platform-browser@7.2.15 but none is installed. You must install peer dependencies yourself.
npm WARN The package @magic-xpa/cli is included as both a dev and production dependency.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
 
npm WARN @angular/http@7.2.15 requires a peer of @angular/core@7.2.15 but none is installed. You must install peer dependencies yourself.
npm WARN @angular/http@7.2.15 requires a peer of @angular/platform-browser@7.2.15 but none is installed. You must install peer dependencies yourself.
npm WARN @magic-xpa/angular@4.6.0 requires a peer of ng-dynamic-component@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @magic-xpa/angular@4.6.0 requires a peer of rxjs@^6.5.2 but none is installed. You must install peer dependencies yourself.
npm WARN ng-dynamic-component@3.1.2 requires a peer of @angular/common@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-dynamic-component@3.1.2 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN The package @magic-xpa/cli is included as both a dev and production dependency.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\karma\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})


Re: MagicXPA45 Webclient install failure

Florian Groothuis
 

I have a feeling that there is something buggy with either the latest Angular version or XPA46. 
Today I did the SPA-tutorial. All went well until routing came up. As soon as XPA's routing comes in play Chrome shows blank pages. I also tried my own simple app, same thing. Opening page is just fine, a button routing to a new program fails. 

The app.routes.ts shows:

export const routes: Routes = [
 
    {
        path: 'Login',
        component: RouterContainerMagicComponent,
        outlet: 'MainOutlet',
 
    },

The Chrome-debugger shows:

core.js:6014 ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'Login'
Error: Cannot match any routes. URL Segment: 'Login'



And I have to make a demo in a few weeks...


Re: Silly IDE question - Separate panels

Brenda Bullorini
 

Thank you Achim!
That worked too.

4401 - 4420 of 196084